main: create jekyll lander if necessary#5024
Conversation
copy lander of preceding version and adjust version in lander
|
Needs to wait for |
|
Now Linkspector works, but npmjs.org refuses to let it access a package that we mention in the style guide:
This might be a temporary problem, after all the same check worked fine with But I strongly dislike things that randomly fail. I could change the style guide and reference the packages Github repository https://github.com/DavidAnson/markdownlint instead, hoping that Github will not deny a Github workflow access to one of its repos 😎 Or I could change the Linkspector configuration and add Or I could exclude the style guide from the link check 😢 Not quite sure which alternative I dislike least 🙄 @lornajane @handrews Any preferences? |
2 participants
The spec site needs Markdown lander pages for showing the latest schema iterations with syntax highlighting, for example https://spec.openapis.org/oas/3.2/schema/2025-09-17.html.
Up to now these files had to be manually created when schemas were published the first time for a MAJOR.MINOR spec version, for example via
Now these lander pages are created by copying the corresponding lander page from the preceding spec version and adjusting it to match the newly published MAJOR.MINOR spec version.
Note
Whenever a new (major) spec version changes the way the schema files are named or structured, lander pages for schema files with new names have to be manually created, and copied lander pages may need to be updated if the purpose of the schema file has changed.